Action Plan for Certificate and Key Renewal

This document outlines the procedure for renewing SSL certificates and software keys for critical systems, specifically focusing on LoadTracking.com and MileMaker, to prevent service disruptions due to expirations. This plan will be executed by the Tampa Transport Support team and external contractors, ensuring proactive management and minimizing risks.

I. General Procedure (Applies to both Certificates and Keys)

Proactive Monitoring: Implement automated alerts for upcoming certificate and key expirations. These alerts should be triggered at least 60 days, 30 days, 14 days, 7 days, and 1 day before the expiration date. The alerts should be sent to the Tampa Transport Support team distribution list.
Change Request Creation: Before any renewal activity, a Change Request must be created in ServiceNow. This ensures proper tracking, approvals, and documentation.
Communication: Maintain clear communication with all stakeholders throughout the renewal process.
Documentation: All steps taken during the renewal process, including CR numbers, dates, times, and any issues encountered, must be documented in the CR and in a central repository (SharePoint).
Post-Renewal Validation: After the renewal, thoroughly test the affected systems to ensure functionality and stability.

II. Specific Procedures

A. SSL Certificate Renewal (e.g., LoadTracking.com)

Change Request: Create a Change Request in ServiceNow (see Section III for required fields).
Vendor Coordination: Contact the vendor (e.g., McLeod Software) to obtain the new certificate and any necessary instructions.
Implementation: Deploy the new certificate to the production server (e.g., LoadTracking.com server). Follow the vendor's instructions carefully.
Validation: Verify that the website (e.g., LoadTracking.com) is accessible and functioning correctly.

B. Software Key Renewal (e.g., MileMaker)

Change Request: Create a Change Request in ServiceNow (see Section III for required fields).
Vendor Communication: Contact the vendor (e.g., MileMaker) to request the new key.
Implementation: Apply the new key to the software.
Validation: Verify that the software is functioning correctly.

III. Change Request Required Fields (Copy-Paste Ready)

A. LoadTracking.com SSL Certificate Renewal Example:

Business Justification: Renewal of the LoadTracking.com SSL certificate is critical...
Implementation Plan: Obtain the new certificate from McLeod Software...
Risk and Impact Analysis: The primary risk is service disruption...
Rollback Plan: If issues arise after the certificate deployment...
Test Plan: Access LoadTracking.com from different browsers...

B. MileMaker Key Renewal Example:

Business Justification: Renewal of the MileMaker software key...
Implementation Plan: Obtain the new key from MileMaker...
Risk and Impact Analysis: The primary risk is service disruption...
Rollback Plan: If issues arise after the key update...
Test Plan: Users will log in to MileMaker...

IV. Contact Information

CEMEX: Christopher George Miller, Dario Garay, Alberto Castaneda Garcia, Jafet Sánchez Celis, Laura Starr
McLeod Software: Adam Clayton
MileMaker: Kyle Williams, Juliana Deleon